Method, process and system for optimized outcome driven workflow synthesis and reduction

ABSTRACT

A process and system is disclosed to assist work planners by assembling a work breakdown structure (WBS) and work flow for a project based on the explicit selection or de-selection of outcome(s) by a work planner from a defined set of possible outcomes. The process and system ensure that the resulting project WBS and work flow is composed of the minimum set of activities required to produce the set of outcomes desired for the project. The process and system further ensure that the project&#39;s activities are organized into an activity hierarchy defined by a WBS template designated by the work planner, and that each of the project&#39;s activities is linked into an appropriate work flow, supported by appropriate instructional content.

[0001] This application claims the benefit of Provisional Applications60/187,481 filed on 7 Mar., 2000 and 60/198,915 filed on 20 Apr. 2000.

FIELD OF INVENTION

[0002] This invention relates to intelligent project planning andexecution and to optimized project planning procedures.

BACKGROUND OF THE INVENTION

[0003] Project planning is a discipline focused on determining,structuring, and scheduling the minimum work necessary to produce theoutcomes defined for the scope of the project in the least amount oftime under known constraints (e.g., resource availability, regulatoryrequirements, etc.).

[0004] Planning complex projects often requires the synthesis,scheduling, and coordination of the activities of many individualshaving expertise in distinct disciplines or professions.

[0005] In most cases, each discipline or profession will have developed,and formally documented, a body of knowledge that is considered toexpress its best practices. Generally, each body of knowledge willdescribe proven and optimal approaches used to achieve specific outcomesassociated with the discipline or profession (e.g., the extraction of awisdom tooth by a dental surgeon, or the design of a user interface fora computer software application by a software engineer).

[0006] The approaches described are typically represented in the body ofknowledge as a series of interdependent activities.

[0007] Combining the activities from more than one body of knowledgeinto a coherent and optimal whole, as represented by a project workbreakdown structure (WBS) and work flow, to satisfy the set of outcomesanticipated by the scope of the project can be daunting, given that theproject planner must rationalize, synthesize, and set dependenciesbetween hundreds or thousands of discrete activities from the bodies ofknowledge involved, without having the benefit of expertise in all ofthe disciplines or professions.

SUMMARY OF THE INVENTION

[0008] The invention comprises a method, process and system forsynthesizing an optimized process flow, an activity abstractionhierarchy and an instruction set that represents the minimal work toproduce at least one outcome. An embodiment of this invention utilizes asingle set of non-redundant activities and activity dependencies, whichhas already been derived from an organization's current processes andprocedures, to produce an optimized work flow with respect to thedesired outcomes for a project. To accomplish this, the conditionalexecution requirements of each activity required to produce a specifiedoutcome are recursively examined to identify the set of activities whichmust be completed to arrive at the outcome. Starting with the last ofthese activities, a determination is made as to whether the activity isalready present in the subject project work plan. If the activity is notpresent, but should be, it is inserted into its correct position in theproject's work breakdown structure and is linked into the work flow foreach predecessor and successor activity already present in the project'swork breakdown structure. Working backward along the process chain fromthat identified last activity, the process of activityinsertion/positioning and work flow linking continues until allactivities in the process chain of the outcome have been considered forinsertion. Higher level summary activities are also introduced into theproject's work breakdown structure as the lowest-level activities areinserted by referencing a designated work breakdown structure template.

BRIEF DESCRIPTION OF THE DRAWINGS

[0009] For a more complete understanding of the present invention, andthe advantages thereof, reference is now made to the followingdescriptions taken in conjunction with the accompanying drawings, inwhich:

[0010]FIG. 1 is a block diagram illustrating an embodiment of theoutcome-driven work planning system;

[0011]FIG. 2 shows the entity relationship diagram for an embodiment ofthe planning system data repository;

[0012]FIG. 3a is a flow chart illustrating the first part of theoutcome-driven work flow synthesis process;

[0013]FIG. 3b is a flow chart illustrating the second part of theoutcome-driven work flow synthesis process;

[0014]FIG. 4a is a flow chart illustrating the first part of theoutcome-driven work flow reduction process;

[0015]FIG. 4b is a flow chart illustrating the second part of theoutcome-driven work flow reduction process;

[0016]FIG. 4c is a flow chart illustrating shows the third part of theoutcome-driven work flow reduction process;

[0017]FIG. 5a is an exemplary WBS Template that is populated with sampledata that is used as the “controlling WBS” in the examples of theOutcome-Driven Work Flow Synthesis and Reduction Processes;

[0018]FIG. 5b is an exemplary project WBS and work flow that ispopulated with sample data following first execution of step 4.1;

[0019]FIG. 5c is an exemplary project WBS and work flow that ispopulated with sample data following second execution of step 4.1;

[0020]FIG. 5d is an exemplary project WBS and work flow that ispopulated with sample data following third execution of step 4.1;

[0021]FIG. 5e is an exemplary project WBS and work flow that ispopulated with sample data following fourth execution of step 4.1;

[0022]FIG. 5f is an exemplary project WBS and work flow that ispopulated with sample data following fifth execution of step 4.1;

[0023]FIG. 5g is an exemplary project WBS and work flow that ispopulated with sample data following sixth execution of step 4.1;

[0024]FIG. 6a is an exemplary project WBS and work flow for all outcomeswithin the scope of the controlling WBS used in examples 1 and 2 of theoutcome-driven work flow synthesis process;

[0025]FIG. 6b is an exemplary project WBS and work flow that ispopulated with sample data following first execution of step 4.1;

[0026]FIG. 6c is an exemplary project WBS and work flow that ispopulated with sample data following second execution of step 4.1;

[0027]FIG. 6d is an exemplary project WBS and work flow that ispopulated with sample data following third execution of step 4.1;

[0028]FIG. 7a shows an exemplary project WBS and work flow used as thestarting point for Example 3: Outcome-Driven Work Flow Reduction Process(i.e., before the reduction of Outcome O2);

[0029]FIG. 7b shows an exemplary project WBS and work flow resultingfrom the execution of procedure 5 from Example 3: Outcome-Driven WorkFlow Reduction Process.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

[0030] The following description is of the best mode presentlycontemplated for carrying out the invention. This description is not tobe taken in a limiting sense, but is merely made for the purpose ofdescribing the general principles of the invention. The scope of theinvention should be determined with reference to the claims.

[0031] This mode may be characterized as a rule-based approximation,synthesis, and reduction approach. The planner may start synthesis andreduction with either an empty plan or with a plan that approximates theanticipated final work breakdown structure and work flow required forthe scope of the project being planned. The approximation can be chosenfrom a set of known and useful “stock” plans. A “stock” plan is apreviously constructed work breakdown structure (WBS) and work flow(with component activities linked to appropriate instructional content),which have proven useful on past projects. Each stock plan describes thework necessary to achieve one or more outcome. In the synthesis andreduction approach one develops a custom work flow by synthesizing thework flows necessary to achieve desired outcomes not present in the planand by de-synthesizing, or reducing, the plan's work flows by removingactivities that are solely required for outcomes which are currentlypresent in the plan, but which are not wanted.

[0032] A process and system is disclosed to assist work planners byassembling a work breakdown structure (WBS) and work flow for a projectbased on the explicit selection or de-selection of outcome(s)by a workplanner from a defined set of possible outcomes. The process and systemensure that the resulting project WBS and work flow is composed of theminimum set of activities required to produce the set of outcomesdesired for the project.

[0033] The process and system further ensure that the project'sactivities are organized into an activity hierarchy defined by a WBStemplate designated by the work planner, and that each of the project'sactivities is linked into an appropriate work flow, supported byappropriate instructional content.

[0034] In cases where the projects undertaken require different sets ofoutcomes, and where the work needed for one outcome may satisfy some orall of the work needed for another outcome, the determination of arigorously optimized WBS and work flow to produce a desired set ofoutcomes (where hundreds or thousands of work steps are involved)is nottypically feasible.

[0035] The present embodiment leverages the manufacturing andinformation technology principles of interchangeable/reusable componentsby recognizing that a single, non-redundant set of activities andactivity dependencies can be derived from multiple formally documentedbodies of knowledge and that this set of activities and activitydependencies can be used to assemble optimized project work breakdownstructures (WBSs) and work flows based on the work planner's selectionand/or de-selection of outcomes to be achieved by the project beingplanned.

[0036] In this context, an “optimized” WBS and work flow for a projectmeans a WBS and work flow that is composed of the minimum set ofactivities necessary to produce the set of outcomes desired by theproject.

[0037] The outcome-driven work flow synthesis process provides a systemand method for the work planner or other user to implement thefollowing:

[0038] 1) View the available WBS templates;

[0039] 2) View outcomes within and outside of the scope of each WBStemplate;

[0040] 3) Choose and transmit a “controlling” WBS template selection;

[0041] 4) Choose and transmit one or more selected outcome forsynthesis;

[0042] 5) View the resulting WBS and work flow; and

[0043] 6) Link each activity in the activity hierarchy represented by aproject's WBS with the appropriate instructional content.

[0044] The outcome-driven work flow reduction process provides a systemand method for the work planner or other user to do the following:

[0045] 1) View the outcomes currently resulting from an existingproject's WBS and work flow;

[0046] 2) Choose and transmit a selected outcome for removal from theWBS and work flow;

[0047] 3) View the resulting project WBS and work flow.

[0048] Taken together, the outcome-driven synthesis and reductionprocesses provide work planners with the ability to construct and tailorwork breakdown structures and work flows, supported by relevant activitydescriptions (i.e., instructional content), by simply considering andselecting the outcomes that the project is intended to achieve.

[0049] The following terminology is grouped together here as a lexiconfor use in describing embodiments of the invention.

[0050] Activity—a specific unit of work

[0051] Elementary Activity—the smallest unit of work that produces ameaningful result for the project.

[0052] Elementary Activity Dependency—An association between twoelementary activities such that an execution of the first results in astate, or set of conditions, required by the second. The state resultingfrom the execution of an elementary activity is called a post-condition.The state required by a dependent elementary activity is called a“pre-condition”.

[0053] Instructional Content Page—a document (e.g., an HTMLdocument)used to describe the purpose or intent of, and approach to, theconduct of an activity. Each instructional content page may containformatted text, graphics, and hyperlinks to related instructionalcontent

[0054] Non-Elementary Activity —a named grouping of lower-levelactivities (non-elementary or elementary) that serves as an abstractionof its subordinate activities.

[0055] Object Class—a type of person, place, thing, concept, event,association, or condition for which information (in the form ofattribute values and relationships) may be saved and upon whichoperations (actions)may be performed.

[0056] Outcome—a defined result of a process (e.g., a manufactured partor final product, an architectural drawing, a conceptual model, adecision made, a judgement rendered, a presentation delivered, a stateof being achieved).

[0057] Project—an organized undertaking to produce or accomplish one ormore desired outcome from a set of possible outcomes.

[0058] Project Activity—represents the use of an elementary activity ornon-elementary activity by a project.

[0059] Project Activity Dependency—represents the use of an elementaryactivity dependency in the workflow for a project.

[0060] Project Planning—a discipline focused on determining,structuring, and scheduling the minimum work necessary to produce theoutcome(s) defined for the scope of the project in the least amount oftime under known constraints (e.g., resource availability, regulatoryrequirements).

[0061] WBS Activity—defines the use and positioning (i.e., verticalpositioning and indention level) of an activity in a WBS template.

[0062] WBS Template—a named hierarchical structure used as a pattern fororganizing project activities into a work breakdown structure (WBS).

[0063] Work Breakdown Structure (WBS) —a hierarchy of project activitiesused to view and manage the work of a project at different levels ofabstraction.

[0064] Work Flow—a network of interdependent elementary activities thatterminates in the elementary activity associated with the production ofan outcome.

[0065] This workflow development process is designed for use onlarge-scale projects, including analysis of business strategies, such aswhere to go with new product development, reorganization of alarge-scale enterprise (e.g. large corporation). Therefore, the resultsof the workflow development process must be without error and must becapable of handling inputs from disparate sources, e.g., in acorporation, from a research and development unit or division, amanufacturing unit or division, a human resources unit or units, anupper management oversight unit and a reorganization plan(simultaneously with a reorganization of the corporation for carryingout the major project). The workflow development must be done in amanner such that the risk to the enterprise utilizing the work flowdevelopment process must be minimized, as well as to the risk to aconsulting company providing guidance with its work flow developmentprocess. For example, a work plan development process, if it wereapplied to the development of the B-2 Bomber, would have entailed thereorganization of a corporation to have a whole new large division,staffing such a division, having ongoing research and development input,designing the aircraft with thousands and thousands of specificationsand requirements, a manufacturing unit, again with thousands ofdocumented procedures, test units with thousands of tests and testdocumentation, acceptance tests procedures and manuals for the AirForce. These are extremely complex processes and the costs may be 100'sof billions of dollars

[0066] However, it would be desirable to have a system which, inaddition to the rule based structure, has an additional element oraspect which allows the work breakdown structure of the flow of thework, in the execution of the project, to be optimized. Now, there arepotentially a number of different ways of optimizing the work breakdownstructure, that is, the flowcharts detailing how the work needs to bedone. In this embodiment, one may start with a previously developedproject plan that is considered to be similar to the plan required forthe anticipated project. However, the planner may find that desiredoutcomes are not included in the “stock” plan, and so adds them. Thatis, one selects one or more outcomes for synthesis. Consequently, thework flow for the selected outcome is synthesized into the current workplan. Similarly, irrelevant outcomes may be present, so the plannersubtracts them. Many interdependent elementary activities may beinvolved in achieving the various outcomes. Adding or removing anoutcome requires the readjustment of the project's work flow and workbreakdown structure. One may also start with an empty plan, i.e., a planwith no outcomes, and add outcomes to that empty plan.

[0067]FIG. 1 shows a computer-based system where RAM 12 and ROM 14 areshown. Other components of a computer-based system are shown including acentral processing unit (CPU) 16, a video display unit 18, acommunications port 20, an intermediate server 22, a remote web server24 and a local web server 26. The data storage repository 28 includesActivities 30, Objects 32, Outcomes 34, Projects 36, InstructionalContents 38 and Work Breakdown Structure (WBS) Templates 40.

[0068]FIG. 2 shows the Entity Relationship Diagram (ERD) for theExemplary Planning System Data Repository. Terms having all letterscapitalized (e.g., ELEMENTARY ACTIVITY 58) refer to FIG. 2. Definitionof terms are listed in the lexicon, above.

[0069] The OBJECTS subject area 42 contains OBJECT CLASS 44, which isthe subject of one or more OBJECT EFFECT 48 in the ACTIVITIES subjectarea 46. Each OBJECT EFFECT 48 always results from one ELEMENTARYACTIVITY 58. Each ELEMENTARY ACTIVITY 58 always is a component of oneNON-ELEMENTARY ACTIVITY 56 and may be identified as successor orpredecessor on one or more ELEMENTARY ACTIVITY DEPENDENCY 50. In theOUTCOMES subject area 60, each OUTCOME 62 is produced by an ELEMENTARYACTIVITY 58. In the PROJECT WBS/WORK FLOWS subject area 64, the PROJECT70 is composed of one or more PROJECT ACTIVITY 68, which may beidentified as a predecessor or successor on one or more PROJECT ACTIVITYDEPENDENCY 66. Each PROJECT ACTIVITY 68 may correspond to an ACTIVITY 52which comprises ELEMENTARY ACTIVITY 58 and NON-ELEMENTARY ACTIVITY 56.The INSTRUCTIONAL CONTENT subject area 72 contains CONTENT PAGE 74 whichmay be referenced by one or more WBS ACTIVITY 80 which is in the WBSTEMPLATES subject area 76. Each WBS ACTIVITY 80 always references oneACTIVITY 52 and may override one or more ELEMENTARY ACTIVITY DEPENDENCY50. Each WBS TEMPLATE 78 may provide a controlling WBS for one or morePROJECTS 70.

Outcome-Driven Work Flow Synthesis Process

[0070] This process is initiated when the work planner at step 96 (FIG.3a) confirms one or more OUTCOMES 62 to be produced/achieved by his orher PROJECT 70. This process will introduce all needed ACTIVITYs 58, 56into the PROJECT 70, as PROJECT ACTIVITYs 68, to form an appropriate WBSand workflow. Each PROJECT ACTIVITY 68 will also be linked to theINSTRUCTIONAL CONTENT PAGE 74 that is appropriate for the controllingWBS TEMPLATE 78 selected by the Work Planner. The choice of the WBSTEMPLATE 78 sets the context for the PROJECT 70.

[0071] For each OUTCOME 62 selected by the Work Planner from the set ofpossible OUTCOMES 60, perform the following procedures:

[0072] Procedure 1: From the Planning Data Repository, at step 98 (FIG.3a) the ELEMENTARY ACTIVITY 58 is selected that produces the OUTCOME 62(selected in step 96) the Work Planner wishes to add to his or herPROJECT 70.

[0073] The selected ELEMENTARY ACTIVITY 58 will be the last point, ornode, in the work flow that results in the OUTCOME 62. The last node 94in a work flow is commonly referred to as the “terminal”, or“most-downstream” node. As an example,

[0074] where denotes ELEMENTARY ACTIVITY; and

[0075] of the five ELEMENTARY ACTIVITIES shown, the one furthestdownstream, i.e., in the direction indicated by the downstream arrow, isthe terminal node 94.

[0076] Procedure 2: At step 100 (FIG. 3a) determine whether theELEMENTARY ACTIVITY 58 selected in step 98 has already been included inthe PROJECT 70 as a PROJECT ACTIVITY 68. If it has been included, thenat step 150 select the next desired OUTCOME 62. If it is found, returnto step 98. If it is not found, end the process, at step 152. If it hasnot already been included, insert an entry into the Node ProcessingTable 114 at step 102 representing the ELEMENTARY ACTIVITY 58, asillustrated in the sample table below, and then continue. Sample NodeProcessing Table - 114 Grouping Processed Entry Seq. # Node ID IndicatorIndicator Removal Indicator 1 12387 N N N

[0077] The columns in the Node Processing Table (NPT) 114 (FIGS. 3a, 3b) are defined as follows: “Entry Seq #” records the insertion order, orsequence, of entries (i.e., rows) in the Node Processing Table. “NodeID” records the unique identifier for an ELEMENTARY ACTIVITY 58 thatparticipates as a node in the OUTCOME's 62 workflow. “GroupingIndicator” indicates whether the ELEMENTARY ACTIVITY 58 is classified asa “grouping” activity. A grouping activity is one that collects, orgroups, other OUTCOMEs 62. Grouping activities are treated in aspecialized way in the Outcome-Driven Work Flow Synthesis Process.“Processed Indicator” indicates whether all processing related to thenode has been completed. This column is set to “N” when entries areinserted into the table, and is changed to “Y” when all processingrelated to the node has been completed. The column “Removal Indicator”is not used for Outcome-Driven Work Flow Synthesis. Instead, this columnis used in the Outcome-Driven Work Flow Reduction process. The defaultvalue for this column is “N”.

[0078] Procedure 3:. At step 104 the first entry in the Node ProcessingTable 114 is selected. As discussed above, this entry will identify themost downstream node 94.

[0079] Procedure 4: Perform the following procedures 4.1 through 4.4(FIG. 3b) until all nodes have been processed:

[0080] Procedure 4.1: At step 106 (FIG. 3b) a PROJECT ACTIVITY 68 recordis inserted, corresponding to the ELEMENTARY ACTIVITY 58 referenced bythe current node being processed, into the PROJECT 70 by performing theActivity Insertion, Positioning, and Content Linking process (describedbelow).

[0081] Procedure 4.2: If the ELEMENTARY ACTIVITY 58 referenced by thecurrent node being processed at step 108 (FIG. 3b) is not classified asa “grouping” ELEMENTARY ACTIVITY 58 (i.e., the Grouping Indicator in theNode Processing Table =“N”), then at step 110 (FIG. 3b) select itsrelevant upstream nodes. At step 112 (FIG. 3b) insert an entry into theNode Processing Table for each relevant upstream node that is notalready determined to be in the Node Processing Table 114 at step 154.For purposes of this step a “relevant upstream node” is defined as anELEMENTARY ACTIVITY 58 that is identified as a predecessor of theELEMENTARY ACTIVITY 58 referenced by the current node by an instance ofELEMENTARY ACTIVITY DEPENDENCY 50 where the following criteria aresatisfied:

[0082] (1) If the ELEMENTARY ACTIVITY 58 corresponding to the mostdownstream node is within the scope of the controlling WBS (i.e., it isreferenced by a WBS ACTIVITY 80 that is a component of the controllingWBS TEMPLATE 78) then the candidate predecessor must also be referencedby a WBS ACTIVITY 80 that is a component of the controlling WBS TEMPLATE78.

[0083] This criterion ensures that PROJECT ACTIVITYs 68 included in aPROJECT 70 are limited to those that correspond to an ELEMENTARYACTIVITY 58 that is explicitly included in the controlling WBS TEMPLATE78 (i.e., is within the scope boundary established by the controllingWBS TEMPLATE 78).

[0084] (2) The ELEMENTARY ACTIVITY DEPENDENCY 50 identifying thecandidate predecessor must not be overridden by a WBS ACTIVITY 80 forthe controlling WBS TEMPLATE 78 associated with the current node, if oneexists; and

[0085] (3) A PROJECT ACTIVITY 68 corresponding to the candidatepredecessor must not already exist for the PROJECT 70.

[0086] Procedure 4.3: At step 116 (FIG. 3b) set the Processed Indicatorfor the current node to “Y” in the Node Processing Table. This alsopertains to grouping ELEMENTARY ACTIVITIES from step 108.

[0087] Procedure 4.4: At 118 select the next unprocessed node in theNode Processing Table (i.e., lowest entry sequence number where theProcessed Indicator =“N”)-this is referred to as the “current node” inthe subsequent steps. If an unprocessed node is found, repeat theprocessing starting back at step 106. If no unprocessed node is found,then select the next desired outcome (step 150, FIG. 3a) and continueaccording to step 150. Eventually all nodes and all outcomes will beprocessed and the processing will end. Activity Insertion, Positioning,and Content Linking

[0088] When inserting a PROJECT ACTIVITY 68 into the PROJECT 70 that iswithin the scope of the controlling WBS TEMPLATE 78, check if a PROJECTACTIVITY 68 corresponding to its parent WBS ACTIVITY 80 (as defined bythe controlling WBS TEMPLATE 78) is already included in the PROJECT 70.If so, position the PROJECT ACTIVITY 68 being inserted one level belowits parent in its correct position relative to any of its siblings whichare already included in the PROJECT 70. If the parent is not currentlyincluded in the PROJECT 70, determine all missing higher-levelNON-ELEMENTARY ACTIVITYs 56 based on the PROJECT's 70 controlling WBSTEMPLATE 78. All missing higher-level NON-ELEMENTARY ACTIVITYs 56 mustbe included in the PROJECT 70 by inserting corresponding PROJECTACTIVITY's 68 into the PROJECT 70, in their correct relative positionsto their siblings. Once all the missing ancestry (i.e., higher-levelactivities) has been included in the PROJECT 70, insert the PROJECTACTIVITY 68 that corresponds to the ELEMENTARY ACTIVITY 58 one levelbelow its parent in its correct relative position to any of its siblingswhich are already included in the PROJECT 70. Link each PROJECT ACTIVITY68 inserted into the PROJECT 70 to the CONTENT PAGE 74 referenced by theWBS ACTIVITY 80 in the PROJECT's 70 controlling WBS TEMPLATE 78 thatreferences the ACTIVITY 52 corresponding to the inserted PROJECTACTIVITY 68.

[0089] When inserting a PROJECT ACTIVITY 68 into the PROJECT 70 that isnot within the scope of the controlling WBS TEMPLATE 78, check if aPROJECT ACTIVITY 68 corresponding to its parent NON-ELEMENTARY ACTIVITY56 is already included in the PROJECT 70. If so, position the PROJECTACTIVITY 68 being inserted one level below the PROJECT ACTIVITY 68corresponding to its parent NON-ELEMENTARY ACTIVITY 56, as the lastPROJECT ACTIVITY 68 in that parent (positioning relative to siblingswill not be known).

[0090] If not, insert both the PROJECT ACTIVITY 68 corresponding to theELEMENTARY ACTIVITY 58 and a PROJECT ACTIVITY 68 corresponding to itsNON-ELEMENTARY ACTIVITY 56 parent to the end of the PROJECT's 70 WBS 78under a top-level PROJECT ACTIVITY 68 named “Activities to be ManuallyPositioned”.

[0091] Create a PROJECT ACTIVITY DEPENDENCY 66 to document eachdependency between a PROJECT ACTIVITY 68 inserted into the PROJECT 70and any of its predecessor and successor PROJECT ACTIVITYs 68 that havealready been included in the PROJECT 70, based on any ELEMENTARYACTIVITY DEPENDENCYs 50 related to the ELEMENTARY ACTIVITY 58 thatcorresponds to the PROJECT ACTIVITY 68. However, do not create a PROJECTACTIVITY DEPENDENCY 66 to document a dependency in any case where theELEMENTARY ACTIVITY DEPENDENCY 50 for the pairing has been overridden bya WBS ACTIVITY 80 that is a component of the PROJECT s 70 controllingWBS TEMPLATE 78.

Outcome-Driven Work Flow Reduction Process

[0092] This process is initiated when the work planner chooses to removean OUTCOME 62 that is currently planned for his or her PROJECT 70. Onceinitiated, this process will remove any PROJECT ACTIVITYs 68 in thesubject OUTCOME's 62 work flow that does not participate in any Thisprocess is initiated when the work planner chooses to remove an OUTCOMEother planned OUTCOME's 62 work flow currently in the PROJECT 70.

[0093] Procedure 1. From the Planning Data Repository 28, at step 160(FIG. 4a) select the PROJECT ACTIVITY 68 corresponding to the ELEMENTARYACTIVITY 58 that produces the OUTCOME 62 the work planner wishes toremove from the PROJECT 70.

[0094] The selected PROJECT ACTIVITY 68 will be the last point, or node,in the work flow that results in the OUTCOME 62 to be removed. As above,the last node 94 in a work flow is commonly referred to as the“terminal”, or “most-downstream” node.

[0095] Procedure 2. At step 162 insert an entry into the Node ProcessingTable 114 (FIG. 4a) representing the PROJECT ACTIVITY 68, as illustratedin the sample table below, and then continue with step 164. 81. SampleNode Processing Table - 114 Grouping Processed Entry Seq. # Node IDIndicator Indicator Removal Indicator 1 12387 N N N

[0096] The columns in the Node Processing Table (NPT) 114 (FIGS. 3a, 3b, 4 a, 4 b, 4 c) have already been defined, above.

[0097] Procedure 3. At step 164 (FIG. 4a) select the first entry in theNode Processing Table 114. As discussed above, this entry will identifythe most downstream node 94 (above).

[0098] Procedure 4. Perform procedures 4.1 through 4.4 (FIGS. 4b, 4 c)until all nodes have been processed.

[0099] Procedure 4.1: Set the removal Indicator in the Node ProcessingTable for the current node to “Y” in step 190 if one of the following istrue:

[0100] (1) The ELEMENTARY ACTIVITY 58, corresponding to the PROJECTACTIVITY 68, at step 166, identified by the current node, produces anOUTCOME 62, at step 166, which was identified at step 192, as beingselected for removal; or

[0101] (2) The ELEMENTARY ACTIVITY 58 corresponding to the PROJECTACTIVITY 68 identified by the current node, does not produce an OUTCOME62 and the PROJECT ACTIVITY 58 does not have any immediate successorPROJECT ACTIVITY's 68 in the PROJECT 70 that have not been marked forremoval in the Node Processing Table 114, as determined at step 194..This test insures that a PROJECT ACTIVITY 68 that is part of the workflow of another OUTCOME 62 currently included in the PROJECT 70 does notget removed, as determined at step 194. If all the successors have notbeen marked for removal in the Node Processing Table 114, the procedurecontinues to step 170 (FIG. 4c).

[0102] Procedure 4.2: If the ELEMENTARY ACTIVITY 58 identified by thecurrent node being processed at step 170 (FIG. 4c) is not classified asa “grouping” activity and it has been marked at step 172 (FIG. 4c) forremoval,. At step 174 (FIG. 4c) select all of its predecessors accordingto the PROJECT ACTIVITY DEPENDENCYs 66 and at step 176 (FIG. 4b) insertan entry into the Node Processing Table 114 for each selectedpredecessor that is determined, at step 178, to not already have anentry in the Node Processing Table 114

[0103] Procedure 4.3: At step 180 (FIG. 4c) set the Processed Indicatorfor the current node to “Y” in the Node Processing Table 114.

[0104] Procedure 4.4: At step 182 select the next unprocessed node inthe Node Processing Table (i.e., the lowest entry sequence number wherethe Processed Indicator “N”). This is now the current node. If anunprocessed node is found at step 184, then return to step 166 (FIG. 4c)and continue from that step 166.

[0105] Procedure 5: At step 186 remove each PROJECT ACTIVITY 68corresponding to an ELEMENTARY ACTIVITY 58 that is designated forremoval in the Node Processing Table from the PROJECT 70 according tothe Activity Removal process. As this removal process proceeds, whenremoving a PROJECT ACTIVITY 68 from a PROJECT 70, check if it is thelast PROJECT ACTIVITY 68 for its parent in the PROJECT's 70 WBS. If so,remove the PROJECT ACTIVITY 68 and its parent from the PROJECT 70. Whenremoving the parent, check if it was the last child for its parent inthe PROJECTs 70 WBS. If so, remove it and its parent. Continue thischild/parent removal process until a parent PROJECT ACTIVITY 68 that hasother children is found or the last ancestor of the current PROJECTACTIVITY 68 has been removed from the PROJECT 70. The processing ends atstep 188.

EXAMPLE 1 Outcome-Driven Work Flow Synthesis Process

[0106] For this example, the user has selected one outcome, outcome“O3”, for synthesis and has selected the exemplary WBS controllingtemplate shown in FIG. 5a as the controlling WBS for the project. Theprocedures identified below correspond to the numbered procedures in thedescription of the Outcome-Driven Work Flow Synthesis Process, above.

[0107] Procedure 1: Elementary activity EA B1.3 produces the outcomethat the user wants to add to the project (i.e., outcome O3), soelementary activity EA B1.3 is selected from the Planning System DataRepository. See FIG. 5a.

[0108] Procedure 2: Since a project activity corresponding to elementaryactivity EA B I0.3 has not already been included in the project, anentry is inserted into the Node Processing Table: 94. Sample NodeProcessing Table - 114 Grouping Processed Entry Seq. # Node ID IndicatorIndicator Removal Indicator 1 EA B1.3 N N N

[0109] Procedure 3: The first entry is selected (shaded row) in the NodeProcessing Table. 96. Sample Node Processing Table - 114 GroupingProcessed Entry Seq. # Node ID Indicator Indicator Removal Indicator 1EA B1.3 N N N

[0110] Procedure 4: The results of executing procedures 4.1- 4.4 untilall entries in the Node Processing Table have been processed are asfollows:

Following First Execution of Procedure 4.1

[0111] 98. Sample Node Processing Table - 114 Grouping Processed EntrySeq. # Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N N N

[0112] Elementary activity EA B1.3 was identified as the elementaryactivity that produces selected outcome O3. At the conclusion of thefirst execution of step 4.1 the state of the Node Processing Table isshown above and the Project WBS/Work Flow is shown in FIG. 5b.

Following First Execution of Procedure 4.2

[0113] Procedure 4.2 identified EA B1.2 as a “relevant” upstream nodefor the current node (EA B1.3) and inserted an entry reflecting thisinto the Node Processing Table (below) 101. Sample Node ProcessingTable - 114 Grouping Processed Entry Seq. # Node ID Indicator IndicatorRemoval Indicator 1 EA B1.3 N N N 2 EA B1.2 N N N

Following First Execution of Procedure 4.3

[0114] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N N N

[0115] Procedure 4.3 set the value of the Processed Indicator cell inthe Node Processing Table for the current node to “Y”.

Following First Execution of Procedure 4.4

[0116] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N N N

[0117] Procedure 4.4 selected the next unprocessed node in the NodeProcessing table (selected node is indicated as the shaded row in theNode Processing Table). This action caused node EA B1.2 to become the“current” node.

Following Second Execution of Procedure 4.1

[0118] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N N N

[0119] Procedure 4.1 caused EA B1.2 to be inserted into the ProjectWBS/Work Flow in its correct position according to the controlling WBStemplate, and to be linked to its successor, EA B1.3. See FIG. 5c.

Following Second Execution of Procedure 4.2

[0120] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N N N 3 EA B1.1 N N N

[0121] Procedure 4.2 identified EA B 1.1 as a “relevant” upstream nodefor the current node (EA B1.2) and inserted an entry (Entry Sequence # 3in the node processing table, above) reflecting this relevantidentification into the Node Processing Table.

Following second execution of procedure 4.3

[0122] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N Y N 3 EA B1.1 N N N

[0123] Procedure 4.3 set the value of the Processed Indicator cell inthe Node Processing Table for the current node to “Y”.

Following Second Execution of Procedure 4.4

[0124] Sample Node Processing Table - 114 Grouping Processed Entry Seq.# Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EAB1.2 N Y N 3 EA B1.1 N N N

[0125] Procedure 4.4 selected the next unprocessed node in the NodeProcessing table (selected node is indicated as the shaded row in theNode Processing Table). This action caused node EA B1.1 to become the“current” node.

[0126] Processing of procedures 4.1 through 4.4 will continue in thesame manner as described above until all relevant upstream nodes havebeen introduced into the Project WBS/Work Flow according to the ActivityInsertion, Positioning, and Content Linking process This exampleillustrates, below, the internal states of the Node Processing Table andProject WBS/Work Flow for each remaining iteration of 4.4.

Following Third Execution of Procedure 4.1

[0127] 109. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N N N

[0128] See FIG. 5d for the Project WBS/Work Flow.

Following Third Execution of Procedure 4.2

[0129] 111. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N N N 4 EA A2.1 N N N

Following Third Execution of Procedure 4.3

[0130] 112. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N N N

Following Third Execution of Procedure 4.4

[0131] 113. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N N N

Following Fourth Execution of Procedure 4.1

[0132] 114. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N N N

[0133]FIG. 5e shows the Project WBS/Work Flow at this point in thealgorithmic process.

Following Fourth Execution of Procedure 4.2

[0134] 116. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N N N 5 EA A1.3 N N N

Following Fourth Execution of Procedure 4.3

[0135] 117. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N N N

Following Fourth Execution of Procedure 4.4

[0136] 118. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N N N

Following Fifth Execution of Procedure 4.1

[0137] 119. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N N N

[0138]FIG. 5f shows the Project WBS/Work Flow at this point in thealgorithmic process.

Following Fifth Execution of Procedure 4.2

[0139] 121. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N N N 6 EA A1.2 N N N

Following Fifth Execution of Procedure 4.3

[0140] 122. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N N N

Following Fifth Execution of Procedure 4.4

[0141] 123. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N N N

Following Sixth Execution of Procedure 4.1

[0142] 124. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N N N

[0143]FIG. 5g shows the Project WBS/Work Flow at this point in thealgorithmic process.

Following Sixth Execution of Procedure 4.2

[0144] 126. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N N N 7EA A1.1 N N N

Following Sixth Execution of Procedure 4.3

[0145] 127. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7EA A1.1 N N N

Following Sixth Execution of Procedure 4.4

[0146] 128. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7EA A1.1 N N N

Following Seventh Execution of Procedure 4.1

[0147] 129. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7EA A1.1 N N N

[0148]FIG. 5h shows the Project WBS/Work Flow at this point in thealgorithmic process.

Following Seventh Execution of Procedure 4.2

[0149] 131. Node Processing Table - 114 Grouping Processed Entry Seq. #Node ID Indicator Indicator Removal Indicator 1 EA B1.3 N Y N 2 EA B1.2N Y N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7EA A1.1 N N N

Following Seventh Execution of Procedure 4.3

[0150] 132. Node Processing Table - 114 Grouping Processed Removal EntrySeq. # Node ID Indicator Indicator Indicator 1 EA B1.3 N Y N 2 EA B1.2 NY N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7 EAA1.1 N Y N

Following Sseventh Execution of Procedure 4.4

[0151] 133. Node Processing Table - 114 Grouping Processed Removal EntrySeq. # Node ID Indicator Indicator Indicator 1 EA B1.3 N Y N 2 EA B1.2 NY N 3 EA B1.1 N Y N 4 EA A2.1 N Y N 5 EA A1.3 N Y N 6 EA A1.2 N Y N 7 EAA1.1 N Y N

[0152] Procedure 4.4 detected no remaining unprocessed nodes in the NodeProcessing Table. This condition causes the termination of syntheticprocessing.

EXAMPLE 2 of the Outcome-Driven Work Flow Synthesis Process

[0153] In this example, after having selected outcome O3 and seeing theresults in the Project WBS/Work Flow from EXAMPLE 1, above, the userdecides to add Outcome O4. This illustrates how to synthesize anadditional outcome into an existing Project WBS/Work Flow. It also showsthe special processing associated with an Elementary Activity classifiedas a “grouping” activity. The notation follows that of EXAMPLE 1, above.FIG. 6a provides an exemplary Project WBS and work scope of thecontrolling WBS used for this example.

Procedure 1

[0154] Elementary activity EA C 1.3 produces the outcome that the user(work planner) wants to add to the project (i.e., Outcome O4), so it isselected from the planning System Data Repository 18 (FIG. 1).

Procedure 2

[0155] Since a project activity corresponding to elementary activity EAC 1.3 has not already been included in the project, an entry is insertedinto the Node Processing Table as follows: 138. Sample Node ProcessingTable - 114 Grouping Processed Removal Entry Seq. # Node ID IndicatorIndicator Indicator 1 EA C1.3 N N N

Procedure 3

[0156] The first entry is selected in the Node Processing Table. This isillustrated by the shading the entry in the exemplary Node ProcessingTable as follows: 140. Sample Node Processing Table - 114 GroupingProcessed Removal Entry Seq. # Node ID Indicator Indicator Indicator 1EA C1.3 N N N

Procedure 4

[0157] The results of executing procedures 4.1 -4.4 until all entries inthe Node Processing Table have been processed are as follows:

Following First Execution of Procedure 4.1

[0158] 142. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N NN

[0159] Elementary activity EA C1.3 was identified as the elementaryactivity that produces the selected outcome O4. At the conclusion of thefirst execution of procedure 4.1 the state of the Node Processing Tableand Project WBS/Work Flow is as shown above and on FIG. 6b.

Following First Execution of Procedure 4.2

[0160] 144. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N NN 2 EA C1.2 N N N

[0161] Procedure 4.2 identified EA C1.2 as a “relevant” upstream nodefor the current node (EA C1.3) and inserted an entry reflecting thisinto the Node Processing Table.

Following First Execution of Procedure 4.3

[0162] 146. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N N N

[0163] Procedure 4.3 set the value of the Processed Indicator cell inNode Processing Table for the current node to “Y”.

Following First Execution of Procedure 4.4

[0164] 148. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N N N

[0165] Procedure 4.4 selected the next unprocessed node in the NodeProcessing Table (selected node is indicated as the shaded row in theNode Processing Table). This action caused node EA C1.2 to become the“current” node.

Following Second Execution of Procedure 4.1

[0166] 150. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N N N

[0167] Procedure 4.1 caused EA C1.2 to be inserted into the ProjectWBS/Work Flow in its correct position according to the Controlling WBSTEMPLATE, and to be linked to its successor, EA C1.3. Since none of EAC1.3's predecessors are present in the Project WBS/Work Flow, it couldnot be linked to its predecessors at this Point. See FIG. 6c.

Following Second Execution of Procedure 4.2

[0168] 152. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N N N 3 EA C1.1 Y N N

[0169] Procedure 4.2 identified EA C1.1 as a “relevant” upstream nodefor current node (EA C1.2) and inserted an entry reflecting this intothe Node Processing Table.

Following Second Execution of Procedure 4.3

[0170] 154. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y N N

[0171] Procedure 4.3 set the value of the Processed Indicator cell inthe Node Processing Table for the current node to “Y”.

Following Second Execution of Procedure 4.4

[0172] 156. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y N N

[0173] Procedure 4.4 selected the next unprocessed node in the NodeProcessing table (selected node is indicated as the shaded row in theNode Processing Table). This action caused node EA C 1.1 to become the“current” node.

Following Third Execution of Procedure 4.1

[0174] 158. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y N N

[0175] Procedure 4.1 caused EA C1.1 to be inserted into the Project/WBSWork Flow in its correct position according to the Controlling WBSTemplate, and to be linked to its successor, EA C1.2 and to itspredecessor, EA B1.3. See FIG. 6

Following Third Execution of Procedure 4.2

[0176] 160. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y N N

[0177] Procedure 4.2 detected that EA C1.1 was a “Grouping” activityand, as a result, did not attempt identification of relevant upstreamnodes. No entries were inserted into the Node Processing Table and EAC1.1 remains the current node

Following Third Execution of Procedure 4.3

[0178] 162. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y Y N

[0179] Procedure 4.3 set the value of the Processed Indicator cell inNode Processing Table for the current node to “Y”.

Following Third Execution of Procedure 4.4

[0180] 164. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA C1.3 N YN 2 EA C1.2 N Y N 3 EA C1.1 Y Y N

[0181] Procedure 4.4 detected no remaining unprocessed nodes in the NodeProcessing Table. This condition causes the termination of synthesisprocessing.

EXAMPLE 3 Outcome-Driven Work Flow Reduction Process Procedure 1

[0182] Project activity EA A2.5 produces the outcome that the user (workplanner) wishes to remove from the project (i.e., O2), so it is selectedfrom the Planning System Data Repository.

Procedure 2

[0183] An entry is inserted into the Node Processing Table as follows:168. Sample Node Processing Table - 114 Grouping Processed Removal EntrySeq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N N N

Procedure 3

[0184] The first entry is selected in the Node Processing Table(shaded). 170. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N NN

Procedure 4

[0185] Procedures 4.1 through 4.4 are executed until all entries in theNode Processing Table have been processed.

Following First Execution of Procedure 4.1

[0186] 172. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N NY

[0187] Project activity EA A2.5 was identified as the activity thatproduces selected outcome O2. At the conclusion of the first executionof procedure 4.1 the state of the Node Processing Table is as shown.

[0188] Procedure 4.1 set the Removal Indicator for the current node to“Y” because the project activity identified by the current node producesthe outcome selected for removal.

Following First Execution of Procedure 4.2

[0189] 175. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N NY 2 EA A2.4 N N N

[0190] Procedure 4.2 identified EA A2.4 as a predecessor to the currentnode (EA A2.5) according to the project activity dependencies, andinserted an entry reflecting this into the Node Processing Table

Following First Execution of Procedure 4.3

[0191] 177. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N N N

[0192] Procedure 4.3 set the value of the Processed Indicator of thecurrent node in the Node Processing Table to “Y”.

Following First Execution of Procedure 4.4

[0193] 179. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N N N

[0194] Procedure 4.4 selected the next unprocessed node in the NodeProcessing Table (selected node is indicated as the shaded row in theNode Processing Table). This action caused the node EA A2.4 to becomethe “current” node.

Following Second Execution of Procedure 4.1

[0195] 181. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N N Y

[0196] Procedure 4.1 set the Removal Indicator for the current node to“Y” because the project activity identified by the current node does notproduce an outcome and does not have any immediate successors in theProject WBS/Work Flow that have not been marked for removal in the NodeProcessing Table (EA A2.5 is its only successor and EA A2.5 has beenmarked for removal in the Node Processing Table).

Following Second Execution of Procedure 4.2

[0197] 183. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N N Y 3 EA A2.3 N N N

[0198] Procedure 4.2 identified EA A2.3 as a predecessor to the currentnode (EA A2.4) according to Project Activity Dependencies, and insertedan entry reflecting this into the Node Processing Table.

Following Second Execution of Procedure 4.3

[0199] 185. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N N N

[0200] Procedure 4.3 set the value of the Processed Indicator of thecurrent node in the Node Processing Table to “Y”.

Following Second Execution of Procedure 4.4

[0201] 187. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N N N

[0202] Procedure 4.4 selected the next unprocessed node in the NodeProcessing Table (shaded row). Thus EA A2.3 becomes the current node.

Following Third Execution of Procedure 4.1

[0203] 189. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N N Y

[0204] Procedure 4.1 sets the Removal Indictor to “Y” because theproject activity identified by the current node does not produce anoutcome. It does not have any immediate successors in the ProjectWBS/Work Flow that have not been marked for removal in the NodeProcessing table. EA A2.4is its only successor and it has already beenmarked for removal.

Following Third Execution of Procedure 4.2

[0205] 191. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N N Y 4 EA A1.3 N N N

[0206] Procedure 4.2 identified EA A1.3 as a predecessor to the currentnode (EA A2.3) according to the project activity dependencies andtherefore inserted an entry into the Node Processing Table.

Following Third Execution of Procedure 4.3

[0207] 193. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N N N

[0208] Procedure 4.3 set the value of the Processed Indicator for thecurrent node being processed to “Y”.

Following Third Execution of Procedure 4.4

[0209] 195. Sample Node Processing Table - 114 Grouping ProcessedRemoval Entry Seq. # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N N N

[0210] Procedure 4.4 selected the next unprocessed node (shaded) so thatEA A1.3 is the current node.

Following Fourth of Procedure 4.1

[0211] 197. Sample Node Processing Table - 114 Entry Seq. GroupingProcessed Removal # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N N N

[0212] Procedure 4.1 does not set the Removal Indicator for the currentmode to “Y” because the project activity identified by the current modehas immediate successors in the Project WBS/Work Flows that have notbeen marked for removal in the Node Processing Table (i.e., EA A2.1 andEA A2.2).

Following Fourth of Procedure 4.2

[0213] 199. Sample Node Processing Table - 114 Entry Seq. GroupingProcessed Removal # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N N N

[0214] Procedure 4.2 does not insert entries into the Node Removal Tablefor EA A1.3's predecessors because EA A1.3 has not been marked forremoval.

Following Fourth of Procedure 4.3

[0215] 201. Sample Node Processing Table - 114 Entry Seq. GroupingProcessed Removal # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N Y N

[0216] Procedure 4.3 set the value of the Processed Indicator for thecurrent node in the Node Processing Table to “Y”.

Following Fourth of Procedure 4.4

[0217] 203. Sample Node Processing Table - 114 Entry Seq. GroupingProcessed Removal # Node ID Indicator Indicator Indicator 1 EA A2.5 N YY 2 EA A2.4 N Y Y 3 EA A2.3 N Y Y 4 EA A1.3 N Y N

[0218] Procedure 4.4 detected no remaining unprocessed nodes in the NodeProcessing Table. This condition causes the termination of procedure 4'siteration. Processing proceeds with procedure 5 which is the deletion ofnodes marked for removal. See FIG. 7b.

[0219] Although the present invention and its advantages have beendescribed in detail, it should be understood that various changes,substitutions and alterations can be made herein without departing fromthe spirit and scope of the invention as defined by the appended claims.Moreover, the scope of the present application is not intended to belimited to the particular embodiments of the process, machine,manufacture, composition of matter, means, methods and steps describedin the specification. As one of ordinary skill in the art will readilyappreciate from the disclosure of the present invention, processes,machines, manufacture, compositions of matter, means, methods, or steps,presently existing or later to be developed that perform substantiallythe same function or achieve substantially the same result as thecorresponding embodiments described herein may be utilized according tothe present invention. Accordingly, the appended claims are intended toinclude within their scope such processes, machines, manufacture,compositions of matter, means, methods, or steps.

What is claimed is:
 1. A method for synthesizing an optimized processflow, an activity abstraction hierarchy and an instruction set thatrepresents the minimal work to produce at least one outcome, comprisingthe steps of: recursively examining conditional execution requirementsof each activity associated with a specified outcome; identifyingactivities which must be completed to arrive at an outcome; identifyingthe last of said activities; determining if an activity is present in aproject work plan while working backward from the identified lastactivity; adding said activity to said project work plan; if anidentified activity is not present; and introducing summary activitiesby referencing a designated work breakdown structure template, whenrequired, when lowest-level activities are added to the work plan.
 2. Amethod for optimizing a work process flow, comprising a work breakdownstructure and instruction for activities, the work process flowrepresenting the minimal work to produce at least one outcome,comprising the steps of: identifying activities necessary to arrive atthe desired outcome; identifying requirements for each activity;identifying the last of the activities; determining if an activity ispresent in the current work project plan by examining the process flowin a reverse direction from the last activity; adding activities to theproject work plan if an activity necessary to the outcome is notpresent; eliminating an activity from the project work plan if anactivity is unnecessary to the outcome; and reexamining the requirementsand activities to ensure that only necessary requirements and activitiesare present leading to the outcome in light of added or eliminatedactivities.
 3. A process for optimizing a work process flow, comprisinga work breakdown structure and instruction for activities, the workprocess flow representing the minimal work to produce at least oneoutcome, comprising the steps of: storing data and algorithms on anon-volatile storage device; storing data and algorithms in volatilememory device; running algorithms on a computer processor utilizing dataand algorithms from non-volatile storage and from volatile memorydevices; assembling an optimized project work breakdown structurefurther comprising: viewing available work breakdown structuretemplates; selecting a work breakdown structure template as thecontrolling work breakdown structure; selecting at least one outcome forsynthesis; synthesizing a new work breakdown structure by adding atleast one outcome; viewing the resulting work breakdown structure andwork flow; removing a selected outcome from a work breakdown structure;synthesizing a new work breakdown structure by removing at least oneoutcome; viewing the work breakdown structure after the removal of aspecified outcome; and linking each activity in the activity hierarchyrepresented by a specific work breakdown structure with a correspondinginstruction module.
 4. A system for optimizing a work process flow,comprising: means for storing data and algorithms on a non-volatilestorage device; means for storing data and algorithms in volatile memorydevice; means for running algorithms on a computer processor utilizingdata and algorithms from non-volatile storage and from volatile memorydevices; means for storing an initial project work breakdown structureand work flow; means for a storing a set of elementary activities meansfor identifying elementary activities necessary to arrive at the desiredoutcome; means for adding at least one outcome to said initial projectwork breakdown structure; means for processing as input said initialproject WBS and said outcome; means for processing as output theelimination of any activity from the process flow if said activity isunnecessary to all chosen and present outcomes; means for processing asoutput the insertion of any activity into the process flow if saidactivity necessary to an outcome is not present; and means forreexamining requirements and activities to ensure that only necessaryrequirements and activities are present leading to an outcome, in lightof added or eliminated activities.
 5. The system as in claim 4 furthercomprising: an instructional text associated with each activity.
 6. Thesystem as in claim 5 further comprising: means for viewing outcomes ofan existing specific project work plan.
 7. A system for optimizing awork process flow, comprising a work breakdown structure and instructionfor activities, the work process flow representing the minimal work toproduce at least one outcome, comprising: means for storing data andalgorithms on a non-volatile storage device; means for storing data andalgorithms in a volatile memory device; means for running algorithms ona computer processor utilizing data and algorithms from non-volatilestorage and from volatile memory device; means for storing an initialproject work plan; means for adding at least one outcome added to saidproject work plan; means for storing at least one node table, comprisingelementary activities together with their entry sequence number, nodeidentification, grouping indicator, processed indicator and removalindicator; means for processing said table of nodes; and means forprocessing as output each activity to add to the process flow if saidactivity necessary to an outcome is not present.
 8. The system as inclaim 7 further comprising: means for removing at least one outcome fromsaid project work plan; and means for processing for removal from saidproject work plan any necessary elementary activities required toachieve said outcome removed.
 9. A system for synthesizing an optimizedprocess flow, an activity abstraction hierarchy and an instruction setthat represents the minimal work to produces at least one outcome,comprising: means for storing data and algorithms on a non-volatilestorage device; means for storing data and algorithms in volatile memorydevice; means for running algorithm on a computer processor utilizingdata and algorithms from non-volatile storage and from volatile memorydevices; means for assembling an optimized project work breakdownstructure further comprising: means for viewing available work breakdownstructure templates; means for selecting a work breakdown structuretemplate; means for selecting at least one outcome for synthesis; meansfor synthesizing a new work breakdown structure by adding at least oneoutcome; means for viewing the resulting work breakdown structure andwork flow; means for viewing outcomes of an existing specific workbreakdown structure; means for removing a selected outcome from a workbreakdown structure; means for synthesizing a new work breakdownstructure by removing at least one outcome; means for viewing the workbreakdown structure after the removal of a specified outcome; and meansfor linking each activity in the activity hierarchy represented by aspecific work breakdown structure with a corresponding instructionmodule.